Veracity determination through comparison of a geospatial location of a vehicle with a provided data

ABSTRACT

A method, apparatus and system related to veracity determination through comparison of a geospatial location data of a vehicle with a provided data are disclosed. In one aspect, the method of a veracity server associates a provided data of an individual with a vehicle using a processor, determines the geospatial location of a vehicle, correlates a relevance of the geospatial location of the vehicle with the provided data, and determines the veracity of the provided data based on the relevance of the geospatial location of the vehicle to the provided data. The method may also comprise the usage of a geospatial circuit in the vehicle in order to transmit geospatial coordinates as well as a plurality of relevant locational information of the vehicle to the veracity server in order to make a correct veracity determination of the provided data.

FIELD OF TECHNOLOGY

This disclosure relates generally to the technical field of veracity determination, and in one example embodiment, this disclosure relates to a method and system of determining truthfulness of a provided data of an individual through a comparison of a geospatial location of a vehicle with the provided data.

BACKGROUND

An individual may submit an information to an organization (e.g., a financial institution, a judge, a police officer, etc.) to seek an approval from the organization that will benefit the individual. For example, the individual may not know a correct address of a reference and/or an employer when submitting the information to the organization. Other times, the individual may wish to conceal information from the organization in an effort to influence a decision that the organization may be requested to make prior to the approval that will benefit the individual.

The organization may provide the approval (e.g., a loan, a parole, a conditional release) in detrimental reliance on an assurance provided by the individual when providing the information. After the approval, the organization may consult public sources to determine if the information provided by the individual is truthful. However, public sources may not confirm the information provided by the individual is truthful.

Confirming the truthfulness of the information provided by the individual may prove time consuming and/or dangerous in an event that the organization has to take measures to visually verify an association of an address with the individual (e.g., a place of employment, a place of residence, etc.). This can be cost prohibitive. Therefore the organization may be defrauded when the individual fails to be verified as having submitted truthful information to the organization.

SUMMARY

Disclosed are a method, system and apparatus related to veracity determination through comparison of a geospatial location data of a vehicle.

In one aspect, a method of a veracity server includes associating a provided data of an individual with a vehicle by a processor communicatively coupled to a machine-readable memory. The method also includes determining a geospatial location of the vehicle by a geospatial circuit hidden in the vehicle and disclosed to the individual. Further, the method includes correlating, by the processor, a relevance of the geospatial location of the vehicle with the provided data. Furthermore, the method of the processor includes determining a veracity of the provided data based on a history of vehicle occurrences at the geospatial locations and the relevance of the geospatial locations with the provided data.

According to another aspect, a veracity server involves a storage having a provided data of an individual and an identification information of a vehicle. Also, the veracity server involves a geospatial circuit to determine a geospatial location of the vehicle. Further, the veracity server involves a machine-readable memory to correlate a relevance of a geospatial location of the vehicle with the provided data. A processor to determine a veracity of the provided data based on the relevance of the geospatial location of the vehicle with the provided data may also be involved.

In another aspect, a system includes a veracity server to determine a geospatial location of a vehicle by a geospatial circuit. The veracity server also to correlate a relevance of the geospatial location with a provided data and to determine a veracity of an individual based on a relevance of the geospatial location to the provided data. Further, the system includes a vehicle to provide a geospatial location associated with the individual to the veracity server. Furthermore, the system includes a storage to hold vehicle identification and provided data from the individual.

The methods, system, and/or apparatuses disclosed herein may be implemented in any means for achieving various aspects, and may be executed in a form of machine readable medium embodying a set of instruction that, when executed by a machine, causes the machine to perform any of the operation disclosed herein. Other features will be apparent from the accompanying drawing and from the detailed description that follows.

BRIEF DESCRIPTION OF DRAWINGS

Example embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawing, in which like references indicate similar elements and in which:

FIG. 1 is an overview illustrating a veracity server that involves a vehicle, an individual, a geospatial circuit, an interested party, and a provided data, according to one embodiment.

FIG. 2 depicts a chart comprising a plurality of provided data of FIG. 1, according to one embodiment;

FIG. 3 is schematic view illustrating the hardware that may comprise the veracity server of FIG. 1, according to one embodiment.

FIG. 4 is a time lapse diagram depicting the geospatial circuit within the vehicle gathering a location data of the vehicle at three different times throughout a day, wherein the location data is a proximity data, a duration data, a frequency data, and a stop time data, according to one embodiment.

FIG. 5 depicts three different exemplary scenarios of a location data history of the vehicle being stationary at different locations of the provided data, according to one embodiment.

FIG. 6 comprises a validation condition table and a message containing a veracity determination delivered to the individual.

Other features of the present embodiments will be apparent from the accompanying drawings and from the detailed description that follows.

DETAILED DESCRIPTION

Example embodiments, as described below, relate to a method, an apparatus and a system related of veracity determination through comparison of a geospatial location data of a vehicle with a provided data, according to one or more embodiments.

FIG. 1 is an overview of a veracity server 100 that may be used to determine a veracity 102 of a provided data 112 (e.g., names of references, residence address, employer addresses, reference addresses) of an individual 104 (e.g., parolee, sub-prime automotive loan applicant). Veracity determination 102 may be based on a relevance data 106 (e.g., location proximity, vehicle stoppage frequency, time of vehicle stoppage) of a geospatial location 108 (e.g., any place where vehicle becomes stationary) of a vehicle 110 (e.g., vehicle owned by parolee, vehicle purchased on credit) with the provided data 112. The individual 104 may voluntarily offer the provided data 112 to comply with an organization (e.g., parole officer, sub-prime automotive lender, employer). A vehicle identification information (vehicle ID) 114 (e.g., vehicle make and model, license plate, registration information, vehicle identification number (VIN)) corresponding to vehicle 110 may also be provided by the individual and/or may be known by the veracity server 100 (e.g., automotive lender owns vehicles for sale, car rental lot).

In one exemplary embodiment, the individual 104 provides information (e.g., accurate and/or current addresses of references, truthful residence addresses, veracity of reference personnel, current place of employment) in a provided data 112. Further, the individual 104 may be associated with a vehicle 110 at a geospatial location 108. The geospatial location 108 may be considered as a location wherein the vehicle 110 becomes stationary.

In another embodiment of the veracity server 100 in FIG. 1, a Global Positioning Satellite (GPS) 124 may determine the geospatial location 108 of the vehicle 110 through a communication (e.g., National Marine Electronics Association (NMEA) 0183, GPS communication protocols) with a geospatial circuit 116 (e.g., global positioning satellite device). The geospatial circuit 116 may reside in the vehicle 110 and may periodically transmit a location data 118. For example, the location data 118 may comprise information of and/or related to an extended vehicle stoppage, a location of a vehicle stoppage, a duration of a vehicle stoppage, a proximity of vehicle location to a predetermined location, and/or a time of vehicle stoppage, according to one embodiment.

In one embodiment, the geospatial circuit 116 may include an antenna to enable wireless communication to the veracity server 100 via a cell tower 126 and/or network 120. For example, the geospatial circuit 116 may include cellular communication protocols such as Global System for Mobile communications (GSM), Code Division Multiple Access (CDMA), and/or Wi-Fi. Further, the network 120 may be a WLAN, WMAN, WAN, 3G, and/or 4G.

Additionally, an interested party 122 (e.g. sub-prime auto lender, parole officer, etc.) may dictate the relevance data 106 to the veracity server 100 to be considered in the veracity determination 102 of the provided data 112. Furthermore, the interested party 122 may rely on personal discretion to decide to configure relevance data 106 specific to each individual 104 (i.e., strict or lenient criteria may be applied on an individual basis), according to one embodiment.

In another embodiment, the veracity server 100 may be used to determine the veracity 102 of the provided data 112 based on the relevance data 106 of multiple geospatial locations 108 (i.e., many locations may be used in an evaluation) of the vehicle 110. In another such embodiment, the veracity server 100 may be used to determine the veracity 102 of multiple sets of provided data 112 based on multiple geospatial locations 108 of multiple vehicles 110 (i.e., multiple sets of provided data corresponding to different people may be evaluated simultaneously).

FIG. 1 depicts an operational state that the veracity server 100 may embody. The veracity server 100 may receive inputs from the interested party 122, the individuals 104, as well as location data 118 from the respective geospatial circuits 116 (i.e., the geospatial circuits of the multiple vehicles of potentially truthful and/or fraudulent individuals.) In one embodiment, the veracity server 100 may provide an output of the veracity determination 102 according to an analysis of the location data 118 and/or the provided data 112.

Important to FIG. 1, is how the veracity server 100 interfaces with the external environment, namely with any number of vehicles 110 and a variety of geospatial locations 108 that each vehicle 110 may occupy at any given point in time. Also, FIG. 1 shows that the veracity server 100 stores a static data (e.g. provided data 112 and vehicle identification 114), receives dynamic data (e.g. location data 118), and uses both data types in determining the veracity 102 of the provided data 112 associated with individual 104 and/or the vehicle 110.

Further, FIG. 1 depicts a user interface 128 (e.g., a software module for a data processing device, a mobile smartphone application) for the interested party 122 to configure the relevance data 106 and/or manage a portfolio of provided data 112, according to one embodiment. The user interface 128 may be communicatively coupled to the veracity server 100, according to one embodiment.

FIG. 2 is a chart diagram of an example embodiment of provided data 112. In provided data scenario 200, the provided data 112 comprises a place of residence 202, a place of employment 204, and a place of reference personnel 206. In one embodiment, provided data scenario 200 may comprise a truthful embodiment. For example, a borrower may provide accurate and truthful information on an automotive loan application. Or, in a fraudulent embodiment, a borrower may provide inaccurate information such as wrong addresses and/or wrong persons of contact. Each of the provided data 112 may comprise one of an address data 208, a global positioning satellite coordinate data 210, and/or a person of contact, as depicted by FIG. 2.

In another embodiment, the provided data 112 of FIG. 2 may include at least a plurality of personal address data (e.g., place of residence 202 and/or place of employment 204) and reference personnel data (e.g., place of reference personnel 206). Additionally, the provided data 112 may comprise a plurality number of personal address data and reference personnel data that may be truthful, fraudulent, and/or inaccurate. Furthermore, the interested party 122 may decide how many of the personal address data and the reference personnel data may be required in a combination to comprise the provided data 112. Each combination of provided data 112 may be specific to each individual 104, according to one embodiment.

Important of FIG. 2, is the fact that the extent of the truthfulness, fraudulence, and/or accuracy of the provided data 112 may not be known by the veracity server 100 at a time of initial data entry. For example, the borrower provides address data 208 on an auto-loan application and the lender may enter any provided data 112 into the veracity server 100 in order to determine a validity of the provided data 112. At the time of a sale and/or a loan agreement between the lender and the borrower, the lender may be unable to determine the validity of the provided data 112. FIG. 2 shows how the veracity server 100 may be acted upon by a variety of individuals 104 with a variety of personal intentions regarding the accuracy of the provided data 112. For example, the individual 104 may be unemployed and thus may provide a false place of employment 204 on an auto-loan application. In a later stage of the veracity server 100, the veracity determination 102 may become possible through an evaluation of the provided data 112 with the location data 118 collected over a period of time, among other considerations, according to one embodiment.

FIG. 3 is a schematic of the minimum hardware that may comprise the veracity server 100, namely a storage 300, a memory 302, and a processor 304. In one such embodiment, the storage 300 having the provided data 112 of individual 104 and the vehicle ID 114 of the vehicle 110 loads the memory 302 to correlate the relevance data 106 of a geospatial location 108 of the vehicle 110 with the provided data 112. As previously disclosed, the relevance data 106 may be configured by the interested party 122, the location data 118 may be transmitted from the geospatial circuit 116 through the network 120 to the veracity server 100, and the provided data 112 may be provided by the individual 104.

Further, the processor 304 may be used to determine the veracity 102 of the provided data 112 based on the relevance data 106 of the geospatial location 108 of the vehicle 110 with the location data 118. In one particular embodiment, the processor 304 may comprise an algorithm 306 to correlate the data loaded into the memory 302 in order to meet a validation condition 308 (e.g., number of truthful provided data 112 required).

In one embodiment, the validation condition 308 may be satisfied and the processor 304 of veracity server 100 may further determine an approval 310 of the provided data 112. Further, upon approval 310, the veracity server 100 may generate an alert 316 (e.g., email, pop-up message on a smartphone, Short Message Service (SMS) text message, phone call) to at least one of the individual 104 and the interested party 122, wherein the alert 316 may comprise a message 314 that informs of the validation condition 308 being satisfied. In another embodiment where the validation condition 308 may not be satisfied, the processor 304 of veracity server 100 may determine a denial 312 of the provided data 112. Furthermore, upon denial 312, the veracity server 100 may generate alert 316 to the individual 104 and/or the interested party 122, wherein the alert 316 may comprise the message 314 that informs of the validation condition 308 being violated based on the provided data 112.

FIG. 3 most importantly displays how each of the external elements of the veracity server 100 (e.g., interested party 122, individual 104) may interact with the internal hardware in order to provide an output of the veracity determination 102. Also, the approval 310/denial 312 processes disclosed in FIG. 3 demonstrates how one particular embodiment of the veracity server 100 may be used to output information (e.g., messages, alerts, status updates). Furthermore, in FIG. 3, the memory 302 may use a software module wherein the relevance data 106 may become configurable by the interested party 122 and through the user interface 128, according to one embodiment.

FIG. 4 depicts a hypothetical scenario 400 in three different states of an elapsed time period. In one embodiment of the veracity server 100, the geospatial location 108 of the vehicle 110 may be determined based on the geo spatial circuit 116 placed with the vehicle 110 that periodically transmits information to the veracity server 100 via network 120, wherein the transmitted information comprises the location data 118. In one such embodiment of the veracity server 100, the location data 118 may comprise at least one of a proximity data 402 _(1-N) (e.g., closeness of the vehicle stoppage relative to a known address), a stop time data 404 _(1-N), a duration data 406, and/or a frequency data 408 (e.g., number of occurrences at a given location). The location data 118 may be relative to the vehicle 110 and the geospatial location(s) 108 of the stationary states, wherein the location data 118 may be recorded and/or transmitted by the geospatial circuit 116, according to one embodiment.

According to another embodiment, scenario 400A occurs at a stop time data 404 ₁ (12:00 AM). FIG. 4 indicates the proximity data 402 ₁ as being the distance between vehicle 110 and the place of residence 202 when the vehicle 110 has become stationary at stop time data 404 ₁, according to one embodiment. In another such embodiment, scenario 400B occurring at 6:00 AM, the state of the vehicle 110 has changed from stationary to mobile (e.g., individual 104 leaves residence in vehicle 110 headed to place of employment). A change in the state of motion of vehicle 110 yields a duration data 406, comprising the total time that has elapsed while the vehicle 110 was in a stationary state at the geospatial location 108 of the place of residence 202. According to the final embodiment of FIG. 4, scenario 400C occurring at 5:00 PM, the vehicle 110 becomes stationary at place of residence 202 once again, generating both a new stop time data 404 ₂ and a new proximity data 402 ₂. An additional frequency data 408 which may comprise the number of vehicle 110 occurrences at a given geospatial location 108 may also be recorded and transmitted in scenario 400C.

The geospatial circuit 116 accomplishes the transmission of location data 118 wherein the location data 118 may comprise at least any number and/or any combination of the data disclosed above, according to one embodiment. Further, the geospatial circuit 116 may transmit location data 118 at a frequency desired by the interested party 122. Furthermore, the location data 118 may comprise the geospatial location 108 of vehicle 110 with respect to any of the provided data 112 and/or may be associated with the vehicle 110, according to one embodiment.

FIG. 4 demonstrates how the geospatial circuit 116 may be utilized by the veracity server 100 to gather location data 118 from the environment of the vehicle 110, according to one embodiment. Another embodiment of the veracity server 100 may comprise a single transmission of location data 118 of each of the distinct types presented in FIG. 4. It will be appreciated that the depicted embodiment of FIG. 4 may be considered as only one of a plurality of possible embodiments of the veracity server 100 and the location data 118.

Further, a tolerance threshold of each type of the location data 118 may be configured by the interested party 122 through the user interface 128, according to one embodiment. According to one embodiment, the relevance data 106 may comprise a plurality of tolerance thresholds in order to determine how relevant a quality of the location data 118 may be in validating the provided data 112.

FIG. 5 demonstrates three hypothetical embodiments of the veracity server 100 and of the location data 118, wherein locational scenarios 500A, 500B, and 500C are example embodiments of the previously disclosed provided data scenario 200 of FIG. 2. Additionally, included in each scenario is a location data history table 502 which comprises an exemplary proximity data 402 _(1-N), stop time data 404 _(1-N), duration data 406, and frequency data 408. Further, a location veracity 504 is depicted with respect to each location and the nature of the location data history table 502.

In one such embodiment, locational scenario 500A shows vehicle 110 at the geospatial location 108 ₁ of the place of residence 202, which may be disclosed in provided data 112. According to this embodiment, the location data history table 502 ₁ displays a hypothetical cumulative history of the vehicle 110 at geospatial location 108 ₁, in terms of the location data 118. The left column of table 502 comprises the type of location data 118, according to one embodiment. The right column of table 502 is an example of the location data 118 accumulated over time at the depicted geospatial location 108, according to one embodiment.

For example, in location data history table 502 ₁, the duration data 406 of the vehicle 110 at this location reads “AVERAGE: 14 hours”. In one embodiment of veracity server 100, an average of the durations of time elapsed while the vehicle 110 resides stationary may be utilized to determine the location veracity 504 ₁ based on the relevance data 106. The place of residence 202 may be found truthful since the vehicle 110 spends large amounts of time on average at the geospatial location 108 ₁ of the place of residence 202 in the provided data 112.

In another example of the location data history table 502 ₁, the frequency data 408 displays a sample of “40 stops per month” corresponding to the number of occurrences of vehicle 110 at geospatial location 108. Additionally indicated by the location data history table 502 ₁, are a proximity data 402 _(1-N) of “Less than ¼ mile” and a stop time data 404 _(1-N) with multiple stop times indicated. In the example embodiment of locational scenario 500A, the veracity server 100 determines that the location data 118 comprising the location data history table 502 ₁ strongly corresponds to the place of residence 202. Thus, the veracity of the provided data 112 may be validated in regards to the place of residence 202 of the provided data 112.

In another embodiment, locational scenario 500B depicts the vehicle 110 at the place of employment 204 that may be in the provided data 112 of the individual 104. The location data history table 502 ₂ is structured in the same way as 502 ₁ and displays resultant location data 118 in regards to vehicle 110 being at the geospatial location 108 ₂ of the place of employment 204, which may be disclosed in the provided data 112. Upon an examination of the results in table 502 ₂, the location history of vehicle 110 likely corresponds to that of a truthful place of employment 204 (e.g., see 502 ₂, stop time data 404 and frequency data 408). Thus, in an exemplary embodiment such as locational scenario 500B, the veracity server 100 determines that the location data 118 of the vehicle 110 corresponds to the place of employment 204. Thus, the veracity of the provided data 112 may be validated in regards to this particular aspect of the provided data 112.

In another embodiment of FIG. 5, locational scenario 500C depicts the vehicle 110 at the place of reference personnel 206 that may be in the provided data 112 of the individual 104. The location data history table 502 ₃ is structured in the same way as 502 ₁ and displays location data results in regards to vehicle 110 being at the geospatial location 108 ₃ of the place of reference personnel 206. Upon an examination of the results in table 502 ₃, the location history of vehicle 110 does not suggest that the place of reference personnel 206 conclusively corresponds to a strong reference address. For example, frequency data 408 indicates that the vehicle only visited geospatial location 108 ₃ only once during the span of one year. Further, the stop time data 404 indicates that the vehicle visited at 1:00 AM. Each of these characteristics indicate that the place of reference personnel 206 may not be an acceptable location of reference to the interested party 122. Thus, in an example embodiment such as locational scenario 500C, the veracity server 100 determines that the location data 118 of the vehicle 110 corresponds to the place of reference personnel 206. Thus, the locational veracity 504 ₃ of the place of reference personnel 206 may be invalidated in regards to this particular aspect of the provided data 112.

The exemplary embodiments of FIG. 5 may be considered as embodiments wherein the provided data 112 may be mostly truthful and/or accurate. However, it may be appreciated that the veracity server 100 may function accordingly in an embodiment where the individual 104 has provided false information and/or inaccurate information. For example, if the individual 104 provided a false place of employment 204, the location data history table 502 may conclude that the pertaining information is false based on location data 118 accumulated over a period of time, according to one embodiment. Or, if the borrower provides a false place of residence 202 on an auto-loan application in an attempt to mislead the lender, then the veracity server 100 may conclude that the vehicle 110 never visits the geospatial location 108 of the indicated place of residence 202. Thus, in a likewise manner to the previously disclosed embodiments, the location veracity 504 may be invalidated. Further, in embodiments such as the previously disclosed embodiments of FIG. 5 or in embodiments where the vehicle 110 does not correspond to the geospatial locations 108 of the provide data 112, the veracity server 100 may be able to determine which geospatial locations 108 of the provided data 112 are valid.

FIG. 6 depicts a validation condition table 600 that refers to the previously disclosed embodiments of FIG. 5. In one embodiment, the validation condition table 600 comprises the location veracity 504 of each of the locational scenarios 500 of FIG. 5. According to one embodiment, validation condition table 600 may be used by the processor 304 to generate the message 314 based on the concluded location veracity 504 of each of the locations of the provided data 112. The message 314 may communicate the results of the veracity sever 100 to the individual 104. The individual 104 may be instructed to contact the lender immediately and/or may be notified of validated addresses of provided data 112. In another embodiment, the message 314 may also be delivered to the interested party 122.

In another embodiment, the number of validated locations 504 of the provided data 112 that are required for approval 310 may be determined at the discretion of the interested party 122. For example, the interested party 122 may determine that only half of the addresses in the provided data 112 need to be validated. Furthermore, in another embodiment, the interested party 122 may decide on an importance level of a specific address in the provided data 112. For example, the interested party 122 may decide that if the place of employment 204 may be determined fraudulent, then the provided data 112 may be given the denial 312 regardless of the veracity of the other locations of the provided data 112.

An example will now be described in which the various embodiments will be explained in a hypothetical scenario. A hypothetical used-car dealer, “XYZ Dealer”, may frequently lend vehicles out to customers with poor credit. Due to the poor credit rating of a customer, XYZ Dealer may require that the customer provide multiple reference address (e.g. place of residence, place of employment, place of reference personnel) on a loan application, wherein accurate address data is required for each case.

In an event where the customer has been found in breach of contract (e.g. frequent late payments, large sum of back payment, failing to make a payment), XYZ Dealer may wish to repossess the vehicle on loan to the customer. In a hypothetical proceeding of vehicle repossessing, XYZ Dealer may rely on the accuracy place of residence address provided in the loan application by the customer. Additionally, XYZ Dealer may rely on the persons of reference and the accuracy of the associated addresses provided in the loan application by the customer. Furthermore, XYZ Dealer may discover throughout the process of vehicle repossession that the customer has in fact provided fraudulent addresses for the place of residence, place of employment, reference personnel, etc. If this is the case, the extent that XYZ Dealer is defrauded may range from not receiving a payment to the extremity of never being able to repossess the vehicle.

Since the problem of inaccurate reference data on a loan application may frequently occur for XYZ Dealer, a veracity server, similar to the one disclosed above, may be employed to fix this problem. In a hypothetical scenario, a customer of XYZ Dealer signs a loan agreement with XYZ Dealer to finance the purchase of a vehicle. The customer fills out the application fraudulently with a purposeful intent to mislead XYZ Dealer as it relates to reference information. In an effort to safeguard against customer fraud, XYZ Dealer discloses in the loan agreement the use of the veracity server to validate the customer and that a geospatial circuit and/or a transmitter are hidden in the vehicle. Further, XYZ Dealer inputs the address data into the storage of the veracity server. Furthermore, XYZ Dealer may choose to configure, through a software module, a level of relevance regarding how strict the correlation must be between the addresses provided by the customer and the location data transmitted from the geospatial circuit.

As the fraudulent customer uses the vehicle throughout the period of the loan agreement, the geospatial circuit continuously transmits a history of location data back to the veracity server located at XYZ Dealership. The veracity server keeps a tally of how many times the vehicle occurred at the provided addresses and also notes other data such as time, duration, and proximity. According to how the veracity server is configured by XYZ Dealer, the veracity server may determine whether enough occurrences of the vehicle at the location of at least one of the reference addresses have been recorded in order to determine that a particular address is truthful.

In the hypothetical scenario where the customer provides fraudulent information, the XYZ Dealer will be able to determine very quickly through the veracity server that the customer does not visit the addresses provided on the application (e.g. vehicle does not appear to frequent the address of residency, vehicle never visits address of employer, etc.). XYZ Dealer may then find the customer in a breach of the loan agreement since the XYZ Dealer may be alerted that the loan agreement may comprise false information. Additionally, if the customer is incompliant with the request of the XYZ Dealer to return the vehicle, the veracity server will be able to provide recent location data of the vehicle to XYZ Dealer thus making the repossession of the vehicle easier.

Although the present embodiments have been described with reference to a specific example embodiment, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the various embodiments. For example, the various devices and modules described herein may be enabled and operated using hardware circuitry (e.g., CMOS based logic circuitry), firmware, software or any combination of hardware, firmware, and software (e.g., embodied in a machine readable medium). For example, the various electrical structure and methods may be embodied using transistors, logic gates, and electrical circuits (e.g., application specific integrated (ASIC) circuitry and/or Digital Signal Processor (DSP) circuitry).

In addition, it will be appreciated that the various operations, processes, and methods disclosed herein may be embodied in a machine-readable medium and/or a machine accessible medium compatible with a data processing system (e.g., a computer device). Accordingly, the specification and drawings are to be regarded in an illustrative in rather than a restrictive sense. 

What is claimed is:
 1. A method of a veracity server comprising: associating, by a processor communicatively coupled to a machine-readable memory, a provided data of an individual with a vehicle; determining, by a geospatial circuit hidden in the vehicle and disclosed to the individual, a geospatial location of the vehicle; correlating, by the processor, a relevance of the geospatial location of the vehicle with the provided data; and determining, by the processor, a veracity of the provided data based on a history of vehicle occurrences at the geospatial locations and the relevance of the geospatial locations with the provided data.
 2. The method of claim 1, further comprising invalidating the veracity of the provided data, wherein the geospatial location of the vehicle may determine the veracity of the provided data, wherein a validation condition may determine to be violated based on the geospatial location of the vehicle, and wherein a generated message may notify an interested party when the validation condition is violated.
 3. The method of claim 2 further comprising, generating an alert based on a status of the validation condition, wherein the alert may notify to at least one of the interested party and the individual, wherein the individual may be alerted at the geospatial location of the vehicle, wherein the alert is at least one of an email, Short Message Service (SMS) text message, voicemail, phone call, and an in-car alert service of the vehicle.
 4. The method of claim 2 further comprising: permitting, by a user interface of the veracity server, the interested party to configure a parameter of relevance associated with an algorithm to be used when correlating the relevance of the geospatial location of the vehicle with the provided data.
 5. The method of claim 4 wherein the parameter of relevance includes at least one of: a duration data of the vehicle at the geospatial location, a frequency data of the vehicle at the geospatial location, a proximity data of the vehicle at the geospatial location, and a stop time data of the vehicle at the geospatial location.
 6. The method of claim 1, further comprising validating the veracity of the provided data, wherein the geospatial location of the vehicle may determine the veracity of the provided data, wherein a validation condition may determine to be satisfied based on the geospatial location of the vehicle, and wherein a generated message may notify an interested party when the validation condition is satisfied.
 7. The geospatial circuit of claim 1, further comprising transmitting information periodically to the veracity server, wherein the geospatial circuit may communicate with a global positioning system (GPS) satellite to obtain geospatial location data, wherein the geospatial circuit may communicate with the veracity server by at least one communication standard including: Global System for Mobile communications (GSM); Code Division Multiple Access (CDMA), wherein the geospatial circuit may receive power from a battery system of the vehicle, and wherein the veracity server determines a report comprising an accumulated location data history of the geospatial circuit.
 8. A veracity server comprising: a storage having a provided data of an individual and an identification information of a vehicle; a geospatial circuit to determine a geospatial location of the vehicle; a machine-readable memory to correlate a relevance of a geospatial location of the vehicle with the provided data; and a processor to determine a veracity of the provided data based on the relevance of the geospatial location of the vehicle with the provided data.
 9. The veracity server of claim 8, wherein the processor: to determine that a validation condition is violated based on the provided data; to determine that the validation condition is violated based on the geospatial location of the vehicle; and to generate a message to an interested party when the validation condition is violated.
 10. The veracity server of claim 9 wherein the processor: to generate an alert to at least one of the interested party and the individual based on a status of the validation condition; and to alert at least one of the interested party and the individual at the geospatial location of the vehicle.
 11. The veracity server of claim 9 wherein a user interface: to permit the interested party to configure a parameter of relevance associated with an algorithm used in correlating the relevance of the geospatial location of the vehicle with the provided data.
 12. The veracity server of claim 11, wherein the parameter of relevance is at least of: a duration data of the vehicle at the geospatial location, a frequency data of the vehicle at the geospatial location, a proximity data of the vehicle at the geospatial location, and a stop time data of the vehicle at the geospatial location.
 13. The veracity server of claim 8 wherein the processor: to determine that the validation condition is satisfied based on the provided data; to determine that the validation condition is satisfied based on the geospatial location of the vehicle; and to generate a message to an interested party when the validation condition is satisfied.
 14. The veracity server of claim 8 wherein the geospatial circuit, hidden in the vehicle and disclosed to the individual, periodically transmits information to the veracity server, wherein the geospatial circuit may communicate with a global positioning system (GPS) satellite to obtain geospatial location data, wherein the geospatial circuit may communicate with the veracity server by at least one communication standard including: Global System for Mobile communications (GSM); Code Division Multiple Access (CDMA), wherein the geospatial circuit may receive power from a battery system of the vehicle, and wherein the veracity server determines a report comprising an accumulated location data history of the geospatial circuit.
 15. A system comprising: a veracity server to determine a geospatial location of a vehicle by a geospatial circuit, to correlate a relevance of the geospatial location with a provided data, and to determine a veracity of an individual based on a relevance of the geospatial location to the provided data; a vehicle to provide a geospatial location associated with the individual to the veracity server; and a storage to hold vehicle identification and provided data from the individual.
 16. The system of claim 15 wherein the veracity server: to determine that a validation condition is violated based on the provided data; to determine that a validation condition is violated based on the geospatial location of the vehicle; and to generate a message to an interested party when the validation condition is violated.
 17. The system of claim 16 wherein the veracity server: to generate an alert to at least one of the interested party and the individual based on a status of the validation condition, and to alert at least one of the interested party and the individual at the geospatial location of the vehicle.
 18. The system of claim 16 wherein the veracity server: to permit, by a user interface, the interested party to configure a parameter of relevance associated with an algorithm used in correlating the relevance of the geospatial location of the vehicle with the provided data.
 19. The system of claim 18 wherein the parameter of relevance is at least of: a duration data of the vehicle at the geospatial location, a frequency data of the vehicle at the geospatial location, a proximity data of the vehicle at the geospatial location, and a stop time data of the vehicle at the geospatial location.
 20. The system of claim 15 wherein the veracity server: to determine that the validation condition is satisfied based on the provided data, to determine that the validation condition is satisfied based on the geospatial location of the vehicle, and to generate a message to an interested party when the validation condition is satisfied. 